language en

Linked.Archi Architecture Processes Extension

Release: 2020-07-27

Modified on: 2026-06-27
This version:
https://meta.linked.archi/arch-processes/0.1.0#
Previous version:
https://meta.linked.archi/arch-processes/0.0.5#
Revision:
0.1.0
Issued on:
2020-07-27
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
See also:
http://dx.doi.org/10.1007/978-3-540-87879-7_14
http://dx.doi.org/10.1016/j.jss.2015.08.054
http://dx.doi.org/10.1109/WICSA.2014.32
https://iasa-global.github.io/btabok/architecture_lifecycle.html
https://www.iso.org/standard/63712.html
https://www.iso.org/standard/68982.html
https://www.iso.org/standard/81702.html
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Linked.Archi Architecture Processes Extension
Provenance of this page
draft

Abstract

Ontology describing architecture governance processes, activities, tasks, and their inputs/outputs — governance infrastructure that acts upon architecture elements, not constituents of the architecture itself.

Linked.Archi Architecture Processes Extension: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Annotation Properties

Linked.Archi Architecture Processes Extension: Description back to ToC

Extension ontology describing architecture governance processes, activities, tasks, and their inputs and outputs. Architecture processes are not constituents of the system being architected — they are the governance and lifecycle infrastructure that acts upon architecture elements from the outside. An architecture review board process governs a system; it is not part of the system's architecture. This extension therefore defines its own class hierarchy independent of arch:Element. Process concepts relate to architecture elements via linking properties (ap:governs, ap:input, ap:output, ap:consumedBy) rather than by subclassing. Use this extension when you need to: * Describe architecture governance processes and their decomposition * Capture process inputs (forces, models, information items) and outputs (decisions, deliverables, models) * Trace how architecture activities relate to decisions and deliverables * Link architecture elements to the processes that govern them The process concepts are aligned with ISO/IEC/IEEE 42020 (architecture governance), ISO/IEC/IEEE 12207 (software lifecycle), and ISO/IEC/IEEE 15288 (system lifecycle). For the normative standard definitions themselves, see the corresponding standard vocabularies under standards/.

Cross-reference for Linked.Archi Architecture Processes Extension classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi Architecture Processes Extension.

Classes

Architecture Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ArchitectureProcess

A process within the architecture governance or lifecycle framework. An architecture process transforms inputs (information items, models, forces) into outputs (decisions, deliverables, models) through a structured set of activities and tasks. Processes can represent governance workflows (e.g., architecture review boards), lifecycle phases (e.g., architecture elaboration), or operational procedures (e.g., change impact assessment). Architecture processes are not part of the architecture being described — they are the governance infrastructure that acts upon it. An architecture review board governs systems; it is not itself a system component.
Example
ex:ArchReviewProcess a ap:ArchitectureProcess ;
    skos:prefLabel "Architecture Review Board Process"@en ;
    ap:hasActivity ex:ReviewPreparation, ex:ReviewExecution, ex:ReviewFollowUp ;
    rdfs:seeAlso <https://meta.linked.archi/iso42020#ArchitectureGovernance> .
is in domain of
governs op, has activity op, has sub-process op, input op, output op, related process op, triggered by op
is in range of
activity of process op, consumed by op, governed by op, has sub-process op, milestone of process op, produced by op, related process op, responsible for op

Information Itemc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#InformationItem

A separately identifiable body of information that is produced, stored, and delivered for human use. Information items are the currency of process communication — they flow between processes as inputs and outputs.
Example
ex:ArchProposal a ap:InformationItem ;
    skos:prefLabel "Architecture Proposal Document"@en ;
    skos:definition "The solution architect proposal including context, options, and rationale."@en ;
    ap:consumedBy ex:ArchReviewProcess .
has super-classes
Process Deliverable c
is in range of
input op, output op

Lifecycle Modelc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#LifecycleModel

A named collection of lifecycle stages defining a complete lifecycle progression for a category of entities. Different domains use different lifecycle models — software products, enterprise applications, technology components, and services each have distinct stage sets. A lifecycle model defines the valid stages and their ordering. Individual entities are associated with a single stage at any point in time.
Example
ex:ApplicationLifecycle a ap:LifecycleModel ;
    skos:prefLabel "Application Portfolio Lifecycle"@en ;
    ap:hasStage ex:Plan, ex:Build, ex:Run, ex:Retire .
is in domain of
has stage op
is in range of
follows lifecycle op, part of lifecycle op

Lifecycle Stagec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#LifecycleStage

A distinct phase in the lifecycle of a system, software product, service, or portfolio item. Lifecycle stages represent states that an entity passes through over time — from initial conception through active use to eventual retirement. Lifecycle stages are not processes — they are the phases within which processes execute. A stage answers "where is it now?" while a process answers "what happens during that phase?"
Example
ex:ActiveStage a ap:LifecycleStage ;
    skos:prefLabel "Active"@en ;
    ap:partOfLifecycle ex:ApplicationLifecycle ;
    ap:stageOrder 3 .
has super-classes
concept c
is in domain of
next stage op, part of lifecycle op, previous stage op, stage order dp
is in range of
at lifecycle stage op, has stage op, next stage op, previous stage op

Process Activityc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessActivity

A cohesive set of tasks within an architecture process that contributes to achieving the process purpose. Activities decompose a process into manageable units of work. An activity groups related tasks and may have its own inputs and outputs. Activities are ordered within a process and may have dependencies on other activities.
Example
ex:StakeholderAnalysis a ap:ProcessActivity ;
    skos:prefLabel "Stakeholder Analysis"@en ;
    ap:activityOfProcess ex:ArchConceptualization ;
    ap:hasTask ex:IdentifyStakeholders, ex:PrioritizeConcerns .
is in domain of
activity of process op, has task op
is in range of
has activity op, task of activity op

Process Deliverablec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessDeliverable

A required output of a process that must be formally delivered to a stakeholder. Deliverables are the tangible work products that result from process execution — documents, models, assessments, or other artifacts.
Example
ex:ArchDefinitionDoc a ap:ProcessDeliverable ;
    skos:prefLabel "Architecture Definition Document"@en ;
    ap:producedBy ex:ArchElaborationProcess .
has sub-classes
Information Item c
is in domain of
produced by op
is in range of
output op

Process Milestonec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessMilestone

A significant point or event in a process that marks the completion of a set of activities or the achievement of a key objective. Milestones are used for governance checkpoints, phase gates, and progress tracking.
Example
ex:ArchReviewGate a ap:ProcessMilestone ;
    skos:prefLabel "Architecture Review Gate"@en ;
    ap:milestoneOfProcess ex:ArchGovernanceProcess .
is in domain of
milestone of process op

Process Rolec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessRole

A role that a stakeholder plays within an architecture process. Process roles define responsibilities and authorities for process execution — who performs, reviews, approves, or is informed about process activities.
Example
ex:ChiefArchitect a ap:ProcessRole ;
    skos:prefLabel "Chief Architect"@en ;
    ap:responsibleFor ex:ArchGovernanceProcess .
has super-classes
stakeholder c
is in range of
approved by op, performed by op

Process Taskc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessTask

A specific action or work item within a process activity. Tasks are the finest-grained units of work in the process decomposition. A task is a requirement, recommendation, or permissible action intended to contribute to the achievement of one or more outcomes of a process.
Example
ex:IdentifyStakeholders a ap:ProcessTask ;
    skos:prefLabel "Identify stakeholders and their concerns"@en ;
    ap:taskOfActivity ex:StakeholderAnalysis ;
    ap:performedBy ex:SolutionArchitect .
is in domain of
task of activity op
is in range of
has task op

Object Properties

activity of processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#activityOfProcess

Links a ProcessActivity to the ArchitectureProcess it belongs to.
has domain
Process Activity c
has range
Architecture Process c
is inverse of
has activity op

approved byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#approvedBy

Links a ProcessDeliverable or ProcessMilestone to the role that approves it.
has range
Process Role c

at lifecycle stageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#atLifecycleStage

Links a resource to the lifecycle stage it currently occupies. Applicable to architecture elements (applications, systems, services) and to architecture models (to indicate elaboration maturity). Domain ontologies may define more specific sub-properties (e.g., timefw:lifecycleState) for their own contexts.
Example
# Application lifecycle
ex:PaymentPlatform a am:ApplicationComponent ;
    ap:atLifecycleStage timefw:Run ;
    ap:followsLifecycle ex:ApplicationLifecycle .

# Architecture work maturity (ISO 42020 phases)
ex:PaymentArchDescription a arch:Model ;
    ap:atLifecycleStage ex:Elaboration .
has range
Lifecycle Stage c

consumed byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#consumedBy

Links an element to the ArchitectureProcess that consumes it as input.
has range
Architecture Process c

followsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#follows

Links a process element to another that must precede it. Used for sequencing activities, tasks, or milestones within a process.
is inverse of
precedes op

follows lifecycleop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#followsLifecycle

Links a resource to the lifecycle model that governs its progression through stages. Applicable to architecture elements and to architecture models.
Example
ex:PaymentPlatform ap:followsLifecycle ex:ApplicationLifecycle .
ex:ApplicationLifecycle a ap:LifecycleModel ;
    skos:prefLabel "Application Portfolio Lifecycle"@en ;
    ap:hasStage timefw:Plan, timefw:Build, timefw:Run, timefw:Retire .
has range
Lifecycle Model c

governed byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#governedBy

Links an architecture element to the ArchitectureProcess that governs it.
has domain
element c
has range
Architecture Process c
is inverse of
governs op

governsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#governs

Links an ArchitectureProcess to the architecture element(s) it governs. The governed elements are constituents of the architecture; the process is the governance infrastructure that acts upon them.
has domain
Architecture Process c
has range
element c
is inverse of
governed by op

has activityop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasActivity

Links an ArchitectureProcess to a ProcessActivity that is part of it. Activities decompose a process into manageable units of work.
has domain
Architecture Process c
has range
Process Activity c
is inverse of
activity of process op

has stageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasStage

Links a LifecycleModel to a LifecycleStage that is part of it.
has domain
Lifecycle Model c
has range
Lifecycle Stage c
is inverse of
part of lifecycle op

has sub-processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasSubProcess

Links an ArchitectureProcess to a child ArchitectureProcess, enabling hierarchical process decomposition.
has domain
Architecture Process c
has range
Architecture Process c

has taskop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasTask

Links a ProcessActivity to a ProcessTask that is part of it.
has domain
Process Activity c
has range
Process Task c
is inverse of
task of activity op

inputop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#input

An information item, model, or artifact consumed by a process. Inputs can include architecture models, metamodels, forces (requirements, constraints), information items, or any other element that feeds into the process.
has domain
Architecture Process c
range includes
force
Information Item c
metamodel
model

milestone of processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#milestoneOfProcess

Links a ProcessMilestone to the ArchitectureProcess it belongs to.
has domain
Process Milestone c
has range
Architecture Process c

next stageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#nextStage

Links a LifecycleStage to the stage that typically follows it in the lifecycle progression.
has domain
Lifecycle Stage c
has range
Lifecycle Stage c
is inverse of
previous stage op

outputop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#output

An information item, model, or artifact produced by a process. Outputs can include architecture models, decisions, deliverables, information items, or any other element that results from process execution.
has domain
Architecture Process c
range includes
decision
Information Item c
Process Deliverable c
metamodel
model

part of lifecycleop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#partOfLifecycle

Links a LifecycleStage to the LifecycleModel it belongs to.
has domain
Lifecycle Stage c
has range
Lifecycle Model c
is inverse of
has stage op

performed byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#performedBy

Links a ProcessActivity or ProcessTask to the role that performs it.
has range
Process Role c

precedesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#precedes

Links a process element to another that must follow it. Used for sequencing activities, tasks, or milestones within a process.
is inverse of
follows op

previous stageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#previousStage

Links a LifecycleStage to the stage that typically precedes it in the lifecycle progression.
has domain
Lifecycle Stage c
has range
Lifecycle Stage c
is inverse of
next stage op

produced byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#producedBy

Links a ProcessDeliverable to the ArchitectureProcess that produces it.
has domain
Process Deliverable c
has range
Architecture Process c

related processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#relatedProcess

Links an ArchitectureProcess to another related process.
has domain
Architecture Process c
has range
Architecture Process c

responsible forop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#responsibleFor

Links a ProcessRole (or Stakeholder) to the ArchitectureProcess they are responsible for executing or governing.
has domain
stakeholder c
has range
Architecture Process c

task of activityop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#taskOfActivity

Links a ProcessTask to the ProcessActivity it belongs to.
has domain
Process Task c
has range
Process Activity c
is inverse of
has task op

triggered byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#triggeredBy

Links a process to the event or condition that triggers its execution. The trigger can be a milestone, a decision, an external event, or a change in the architecture.
has domain
Architecture Process c

Data Properties

stage orderdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/arch-processes#stageOrder

Numeric ordering of a lifecycle stage within its lifecycle model (1-based).

has characteristics: functional

has domain
Lifecycle Stage c
has range
integer

Annotation Properties

abstractap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/abstract

citationap back to ToC or Annotation Property ToC

IRI: http://schema.org/citation

createdap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/created

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

definitionap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#definition

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

exampleap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#example

issuedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/issued

licenseap back to ToC or Annotation Property ToC

IRI: http://creativecommons.org/ns#license

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/modified

pref labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#prefLabel

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

range includesap back to ToC or Annotation Property ToC

IRI: http://schema.org/rangeIncludes

scope noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#scopeNote

statusap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/status

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

was derived fromap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/prov#wasDerivedFrom

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

Changes from last version

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.